On-demand rental of electric vehicles

ABSTRACT

Location data associated with an on-demand electric vehicle and an indication that an on-demand electric vehicle has fallen are received. It is determined that a rental associated with the on-demand electric vehicle has ended. Information indicating that the on-demand electric vehicle is in a fallen position is provided via a user interface.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/544,537, entitled ON-DEMAND RENTAL OF ELECTRIC VEHICLES filed Aug.19, 2019, which claims priority to U.S. Provisional Patent ApplicationNo. 62/765,299, entitled ON-DEMAND RENTAL OF ELECTRIC VEHICLES filedAug. 20, 2018, each of which is incorporated herein by reference for allpurposes.

BACKGROUND OF THE INVENTION

An on-demand electric vehicle may be rented by a user via the user'smobile device. An application associated with the on-demand electricvehicle provider may be installed on the user's mobile device. The usermay use the on-demand electric vehicle provider's application to rentthe on-demand electric vehicle. During a rental period, the user maytravel to any location for which the rented on-demand electric vehiclehas sufficient charge.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a system toprovide on-demand electric vehicles.

FIG. 2 is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle.

FIG. 3A is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle.

FIG. 3B is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle.

FIG. 4A is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle.

FIG. 4B is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle.

FIG. 5A is a flow chart illustrating an embodiment of a process tomaintain on-demand electric vehicles in an up-right position.

FIG. 5B is a flow chart illustrating an embodiment of a process tomaintain on-demand electric vehicles in an up-right position.

FIG. 5C is a flow chart illustrating an embodiment of a process tomaintain on-demand electric vehicles in an up-right position.

FIG. 6A is a flow chart illustrating an embodiment of a process torebalance a plurality of on-demand electric vehicles.

FIG. 6B is a flow chart illustrating an embodiment of a process torebalance a plurality of on-demand electric vehicles.

FIG. 7 is a block diagram illustrating a computer system in accordancewith some embodiments.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

The use of on-demand electric vehicles has proliferated over the pastcouple of years. Examples of on-demand electric vehicles include, butare not limited to, electric scooters, electric bikes, minibikes, motorscooters, motorcycles, skateboards, hover boards, other single- ormulti-wheeled electrically-powered boards, and self-balancing personalelectric vehicles. A user may rent an on-demand electric vehicle througha mobile app associated with the on-demand electric vehicle providerhosted on the user's mobile device. After the user has rented theon-demand electric vehicle, the user is free to use the electric vehicleas the user desires.

However, use of electric vehicles may not be permitted in some contextsand/or restrictions may be placed on their use in some contexts. Forexample, municipalities may pass regulations to regulate the use ofelectric vehicles, e.g., prohibiting or restricting use in certain areasand/or at certain times of day or based on other conditions. Users maynot be aware of and/or may not follow such restriction. For example, auser may attempt to ride the electric vehicle through prohibited area(e.g., a beach boardwalk, a park, sidewalk, etc.). An area may be markedvia one or more signs indicating that electric vehicles are prohibitedor restricted to a stated maximum speed, but users may disregard thesignage. A user may ride the electric vehicle at an inappropriate speedfor a particular context (e.g., time of day, location, weather, trafficconditions, etc.).

Techniques to enforce restrictions on the use of on-demand electricvehicles are disclosed. In various embodiments, an on-demand electricvehicle may configured and/or reconfigured after a user has initiated arental of the on-demand electric vehicle to prevent the user from usingthe on-demand electric vehicle in an undesirable manner. For example,operation of the on-demand electric vehicle may be restricted to preventuse in a prohibited area. The maximum speed of the on-demand electricvehicle may be reduced based on the particular context (e.g., location,time of day, weather, traffic conditions, etc.)

Techniques are disclosed to ensure on-demand electric vehicles remainparked in an upright position. After the user has finished a rental ofthe on-demand electric vehicle, the electric vehicle may be placed in anupright position. Subsequently, the on-demand electric vehicle may betipped over (either accidentally or on-purpose). The on-demand electricvehicle may remain in a fallen position until someone fixes the positionof the fallen on-demand electric vehicle (i.e., place the fallenelectric vehicle in an upright position). Fallen on-demand electricvehicles may be viewed as a nuisance because they may be blockingsidewalks, pathways, or doorways. In various embodiments, an indicationmay be received that one or more electric vehicles are not in an uprightposition. One or more fixers may be provided a notification via a userinterface of the application associated with the on-demand electricvehicle provider. The term “fixer” may refer a person that corrects aposition of an electric vehicle from a fallen position to an uprightposition. The notification may indicate a location of the fallenon-demand electric vehicle(s) and for each a corresponding incentive fora fixer to correct an orientation of an on-demand electric vehicle froma fallen position to an upright position. The orientation of anon-demand electric vehicle may be fixed to prevent the on-demandelectric vehicle from continuing to block sideways, pathways, ordoorways.

On-demand electric vehicles may not be tied to a particular dockingstation. This may allow a user to leave an on-demand electric vehicle inat any location after renting the on-demand electric vehicle. In someembodiments, the location is a low-demand zone (e.g., an area having afrequency of users below a first demand threshold). In some embodiments,the location is a high-saturation zone (e.g., an area having a number ofon-demand electric vehicles available for rental greater than or equalto a saturation threshold). In some embodiments, the location is hightheft/vandalism zone (e.g., an area having a number of theft/vandalismincidents greater than or equal to a theft/vandalism threshold.)

Leaving an on-demand electric vehicle in one of these zones may lead toan inefficient use of the on-demand electric vehicle because theon-demand electric vehicle may remain un-used until it is picked up andrelocated to another location. For example, leaving an on-demandelectric vehicle in a low demand zone may cause the on-demand electricvehicle to remain unused for an extended period of time because demandfor on-demand electric vehicles at the particular location is low.Leaving an on-demand electric vehicle in a high-saturation zone may leadto an inefficient use of the on-demand electric vehicle because thereare too many on-demand electric vehicles for a particular locationdespite the demand for on-demand electric vehicles. Leaving an on-demandelectric vehicle in a high theft/vandalism zone may lead to aninefficient use of the on-demand electric vehicle because a theft of theon-demand electric vehicle prevents any potential users from renting theon-demand electric vehicle and vandalism causes damage to the on-demandelectric vehicle, which renders the on-demand electric vehicleunavailable for use until the damage is repaired.

Techniques to relocate one or more electric vehicles to achieve adesired distribution of vehicles are disclosed. In various embodiments,one or more “rebalancers” may be provided a notification via a userinterface of the application associated with the on-demand electricvehicle provider. The term “rebalancer” may refer a person thatrelocates an electric vehicle from a first location (e.g., aninefficient use zone) to a second location (e.g., efficient use zone).The notification may indicate a location of the on-demand electricvehicle and a corresponding incentive for a rebalancer to relocate anon-demand electric vehicle from a first location to a second location.The on-demand electric vehicle may be relocated to a different locationto prevent the inefficient use of the on-demand electric vehicle.

FIG. 1 is a block diagram illustrating an embodiment of a system toprovide on-demand electric vehicles. In the example shown, the system100 includes a fleet of electric vehicles represented by electricvehicles 102 a, 102 n. Examples of electric vehicles include, but arenot limited to, electric scooters, electric bikes, minibikes, motorscooters, motorcycles, skateboards, hover boards, other single- ormulti-wheeled electrically-powered boards, and self-balancing personalelectric vehicles. Although two electric vehicles are depicted in FIG.1A, the electric fleet may be comprised of n electric vehicles. Theplurality of electric vehicles are available for use “on demand.”

Electric vehicles 102 a, 102 n and other vehicles in the fleet arepropelled by an electric motor (not shown) powered by a battery (notshown), e.g. a battery in the foot board and/or located elsewhere inscooter. The batteries of electric vehicles 102 a, 102 n are depletedthrough use. Charger equipment (not shown) plugged into a power outletor other power source (not shown) may be used to charge the battery ofan electric vehicle.

Each vehicle is equipped with a corresponding computer system (e.g.,computer systems 108 a, 108 n) comprising a communication functionality,such as WiFi, Bluetooth, GPS, cellular, etc., enabling the vehicle toconnect directly or indirectly (e.g., via a user's mobile device) viathe Internet 110 to a backend server 112. The connection may be via adirect wireless connection (e.g., direct wireless connections 116 a, 116n), if equipped, or an indirect wireless connection, (e.g., viaBluetooth or other near field communication (e.g., 118 a, 118 n)), to auser's mobile device (e.g., 114 a, 114 n) configured to relayinformation via wireless connections (e.g., 120 a, 120 n) to the backendserver 112 via the Internet 110. For example, mobile device 114 aassociated with a user may be used to receive vehicle state informationfrom the electric vehicle 102 a and relay such information via theInternet 110 to backend server 112. Mobile devices 114 a, 114 n may havean application associated an on-demand electric vehicle providerinstalled. In some embodiments, mobile device 114 a associated with auser may be used to receive configuration data from the backend server112 and relay such information via the wireless connection 118 a toelectric vehicle 102 a.

In various embodiments, vehicle state information including at least abattery charge level of an electric vehicle, a location of the electricvehicle, an orientation of the electric vehicle (e.g, upright orfallen), or a position of the electric vehicle may be reported from timeto time and/or upon occurrence of certain events to backend server 112.Configuration data may include a maximum speed associated with alocation of the electric vehicle.

A computer system may comprise one or more sensors configured to measureorientation, acceleration, tilt, and/or location (e.g., gyroscope,accelerometer, inclinometer, clinometer, GPS, etc.). In an up-rightposition, an orientation sensor is configured to output a first set ofvalues. In a fallen position, the orientation sensor is configured tooutput a second set of values. Electric vehicles 102 a, 102 n may bedetermined to be in a fallen position based on an output of theircorresponding orientation sensors. In other embodiments, electricvehicles 102 a, 102 n may provide their corresponding orientation datato backend server 112, which may use the corresponding orientation datato determine that an electric vehicle has fallen (e.g., on its side).

In an up-right position, a tilt sensor is configured to output a firstset of values. In a fallen position, the tilt sensor is configured tooutput a second set of values. Electric vehicles 102 a, 102 n may bedetermined to be in a fallen position based on an output of theircorresponding tilt sensors. In other embodiments, electric vehicles 102a, 102 n may provide their corresponding tilt data to backend server112, which may use the corresponding tilt data to determine that anelectric vehicle has fallen (e.g., on its side).

In an up-right position, an acceleration sensor is configured to outputa first set of values. Between the up-right position and a fallenposition, the acceleration sensor is configured to output a second setof values. In a fallen position, the acceleration sensor is configuredto output a third set of values. Electric vehicles 102 a, 102 may bedetermined to be in a fallen position based on an output of theircorresponding acceleration sensors. In other embodiments, electricvehicles 102 a, 102 n may provide their corresponding acceleration datato backend server 112, which may use the corresponding acceleration datato determine that an electric vehicle has fallen (e.g., on its side).

A location sensor may be configured to output location data. Thelocation data may be provided directly from electric vehicles 102 a, 102n to backend server 112 via wireless connections 116 a, 116 n,respectively and the Internet 110. In other embodiments, location datais provided indirectly from electric vehicles 102 a, 102 n to backendserver 112 via mobile devices 114 a, 114 n, respectively, wirelessconnections 120 a, 120 n, respectively, and the Internet 110. In someembodiments, mobile devices 114 a, 114 n provide their correspondinglocation data to backend server. Backend server 112 may use eitherlocation data from an electric vehicle or an associated mobile device todetermine the location of the electric vehicle.

Backend server 112 in various embodiments maintains current and/orhistorical vehicle state information in a vehicle and user data store122, e.g., a database. Vehicle information stored in data store 122 mayinclude without limitation a history of preventive maintenance, repairs,ride and/or other usage history and data, user and/or charger feedbackabout the vehicle and/or its condition, charge state, battery health,current location, orientation (e.g., upright or fallen), etc. Userinformation stored in data store 122 may include without limitationrecords associated with users registered to ride vehicles comprising thefleet, such as electric vehicles 102 a, 102 n, users registered tocharge vehicles comprising the fleet in exchange for a payment and/orother consideration (e.g., ride credits, virtual currency, status orother recognition within a user community, etc.), users registered tofix fallen electric vehicles (e.g., “fixers”) in exchange for a paymentand/or other consideration, and users registered to re-locate electricvehicles (e.g., “rebalancers”) in exchange for a payment and/or otherconsideration. User records for users who charge vehicles (sometimesreferred to as “chargers”) in various embodiments may includeinformation indicating which vehicles are currently being charged (orreserved to be charged) by the user; financial account information;past, current, or expected payment information; charger performancemetrics, such as percent on time redeployment, etc.; etc.

User records for users who fix fallen electric vehicles in variousembodiments may include information indicating which vehicles arecurrently reserved to be placed in an up-right positon by the user;financial account information; past, current, or expected paymentinformation; performance metrics (e.g., time from selection of fallenelectric vehicle to time of fixing the selected fallen electric vehicle,etc.), etc.

User records for users who re-locate electric vehicles in variousembodiments may include information indicating which vehicles arecurrently reserved to be re-located by the user; financial accountinformation; past, current, or expected payment information; performancemetrics (e.g., time from selection of electric vehicle to be relocatedto time of actual relocating electric vehicle, etc.), etc.

Backend server 112 may be configured to update the configuration of arented electric vehicle based a location associated with the rentedelectric vehicle to restrict operation of the rented electric vehicle ina restricted zone. For example, backend server 112 may determine alocation associated with a rented electric vehicle. The determinedlocation may be associated with one or more restricted areas. Backendserver 112 may maintain a map that includes one or more restrictedareas. In some embodiments, backend server 112 receives location dataassociated with a rented electric vehicle and compares the receivedlocation to boundaries associated with one or more restricted areas. Inthe event the received location is in or near a restricted area within athreshold distance, backend server 112 may send configuration data tothe rented electric vehicle to modify a configuration of the rentedelectric vehicle (e.g., reduce a maximum speed or prevent operation). Insome embodiments, the configuration data is directly provided frombackend server 112 to an electric vehicle 102 a, 102 n via wirelessconnections 116 a, 116 n, respectively. In some embodiments, theconfiguration data is indirectly provided from backend server 112 to anelectric vehicle 102 a, 102 n via wireless connections 120 a, 120 n,mobile devices 114 a, 114 n, and wireless connections 118 a, 118 n,respectively. In some embodiments, backend server 112 determines whetherthe rented electric vehicle is capable of entering the one or morerestricted areas based on a remaining amount of charge associated withthe rented electric vehicle and a current location of the rentedelectric vehicle. For example, an electric vehicle may be capable oftraveling 15 miles on a single charge before the electric vehicle needsto be re-charged. Backend server 112 may determine whether the electricvehicle is within 15 miles of any restricted area. In the event therented electric vehicle is capable of traveling to a restricted areausing the remaining amount of charge, backend server may sendconfiguration data to the rented electric vehicle to prevent the rentedelectric vehicle from operating in a restricted area. In response toreceiving the configuration data, the rented electric vehicle isprevented from operating in a restricted area.

Backed server 112 may be configured to update the configuration of arented electric vehicle to reduce a maximum capable speed of the rentedelectric vehicle based on a location associated with the rented electricvehicle. For example, backend server 112 may determine a locationassociated with a rented electric vehicle. The determine location may beassociated with one or more areas subject to speed restrictions. Backedserver 112 may maintain a map that includes the one or more areassubject to speed restrictions. In some embodiments, backend server 112receives location data associated with a rented electric vehicle andcompares the received location to boundaries associated with one or moreareas subject to speed restrictions. In the event the received locationis in an area subject to a speed restriction, backend server 112 maysend configuration data to the rented electric vehicle to modify aconfiguration of the rented electric vehicle (e.g., reduce a maximumspeed). In some embodiments, the configuration data is directly providedfrom backend server 112 to an electric vehicle 102 a, 102 n via wirelessconnections 116 a, 116 n, respectively. In some embodiments, theconfiguration data is indirectly provided from backend server 112 to anelectric vehicle 102 a, 102 n via wireless connections 120 a, 120 n,mobile devices 114 a, 114 n, and wireless connections 118 a, 118 n,respectively. In some embodiments, backend server 112 determines whetherthe rented electric vehicle is capable of entering the one or more areaswith speed restrictions based on a remaining amount of charge associatedwith the rented electric vehicle and a current location of the rentedelectric vehicle. For example, an electric vehicle may be capable oftraveling 15 miles on a single charge before the electric vehicle needsto be re-charged. Backend server 112 may determine whether the electricvehicle is within 15 miles of any area subject to a speed restriction.In the event the rented electric vehicle is capable of traveling to anarea subject to a speed restriction using the remaining amount ofcharge, backend server may send configuration data to the rentedelectric vehicle to reduce a maximum speed associated with the rentedelectric vehicle upon entering an area with a speed restriction. Inresponse to receiving the configuration data, a maximum speed of therented electric vehicle is reduced upon the rented electric vehicleentering an area with a speed restriction. For example, the electricvehicle may be capable of reaching a maximum speed of 15 mph in anon-restricted area and capable of reaching a maximum speed of 7 mph inan area with a speed restriction.

Backend server 112 may be configured to cause a fixer to fix one or morefallen electric vehicles. After a user has finished a rental of theelectric vehicle, the electric vehicle may be placed in an uprightposition. The electric vehicle may be tipped over (either accidentallyor on-purpose). The electric vehicle may remain in a fallen positionuntil someone fixes the position of the fallen electric vehicle (i.e.,place the fallen electric vehicle in an upright position). Fallenelectric vehicles may be viewed as a nuisance because they may beblocking sidewalks, pathways, or doorways.

Backed server 112 may receive an indication that an electric vehicle isno longer in an upright position. For example, backend server 112 mayreceive orientation data or acceleration data that indicates thatelectric vehicle is no longer in an upright position. In someembodiments, an electric vehicle provides a notification to backendserver 112 that indicates the electric vehicle is in a fallen position.

Backed server 112 may update a user interface of an applicationassociated with the on-demand electric vehicle provider that indicatescorresponding locations for one or more fallen electric vehicles. Afixer via the fixer's mobile device may view corresponding locationsassociated with one or more fallen electric vehicles. Each fallenelectric vehicle may have a corresponding incentive. Examples ofincentives include money, credits to use electric vehicles associatedwith the electric vehicle provider, credits to use at a goods provider(e.g., retail provider, food provider, etc.), credits to use at aservice provider (e.g., free car wash, free house cleaning, etc.), etc.

Backend server 112 may receive a selection of one or more fallenelectric vehicles. In response to the selection, backend server 112 mayupdate the user interface of the application associated with theon-demand electric vehicle provider such that the one or more selectedfallen electric vehicles are no longer available for one or more otherfixers to select. Backend server 112 may receive an indication that afallen on-demand electric vehicle is in an up-right position. Forexample, backend server 112 may receive a picture of the fallenon-demand electric vehicle from a mobile device associated with thefixer.

Backend sever 112 may receive from the fallen on-demand vehicleorientation data that indicates the fallen electric vehicle is in anup-right position. Backend sever 112 may receive from the fallen vehicleacceleration data that indicates the fallen electric vehicle is in anup-right position. In response to the electric vehicle being in anup-right position, backend server 112 may provide the incentiveassociated with the fallen electric vehicle to the fixer.

Backend server 112 may be configured to cause a rebalancer to change alocation of one or more electric vehicles. On-demand electric vehiclesmay not be tied to a particular docking station. This may allow a userto leave an electric vehicle in at any location. In some embodiments,the location is a low-demand zone (e.g., a zone having a frequency ofusers below a first demand threshold). This may lead to an inefficientuse of the on-demand electric vehicle because the electric vehicle mayremain un-used until it is picked up and relocated to another location.In some embodiments, the location is oversaturated with other on-demandelectric vehicles (e.g., a location having a number of on-demandelectric vehicles greater than a saturation threshold.). This may alsolead to an inefficient use of the on-demand electric vehicle because theon-demand electric vehicle may remain un-used since there may beinsufficient demand for the plurality of on-demand electric vehicles atthe location. In some embodiments, the location is a location prone totheft and/or vandalism. This may also lead to an inefficient use of theon-demand electric vehicle since a theft of the on-demand electricvehicle prevents any potential users from renting the on-demand electricvehicle. Vandalism may cause damage to the on-demand electric vehicle,which renders the on-demand electric vehicle unavailable for use untilthe damage is repaired. The on-demand electric vehicle may be relocatedto a different location to prevent the inefficient use of the on-demandelectric vehicle.

Each electric vehicle of the electric vehicle fleet associated with anelectric vehicle provider is configured to provide correspondinglocation data to backend server 112. Backend server 112 may use thelocation data to partition a map into a plurality of zones. Theplurality of zones may comprise one or more low-demand zones, one ormore medium-demand zones, and one or more high-demand zones. Alow-demand zone may be comprised of an area having a frequency of usersbelow a first demand threshold. A medium-demand zone may be comprised ofan area having a frequency of users greater than or equal to the firstdemand threshold and less than a second demand threshold. A high-demandzone may be comprised of an area having a frequency of users greaterthan or equal to the second demand threshold.

The plurality of zones may comprise one or more low-saturation zones,one or more medium-saturation zones, and one or more high-saturationzones. A low-saturation zone may be comprised of an area having a numberof electric vehicles available for rental below a first saturationthreshold. A medium-saturation zone may be comprised of an area having anumber of electric vehicles available for rental greater than or equalto the first saturation threshold and less than a second saturationthreshold. A high-saturation zone may be comprised of an area having anumber of electric vehicles available for rental greater than or equalto the second saturation threshold.

The plurality of zones may comprise one or more low theft/vandalismzones, one or more medium theft/vandalism zones, and one or more hightheft/vandalism zones. A low-theft/vandalism zone may be comprised of anarea having a number of theft/vandalism incidents below a firsttheft/vandalism threshold. A medium-theft/vandalism zone may becomprised of an area having a number of theft/vandalism incidentsgreater than or equal to the first theft/vandalism threshold and lessthan a second theft/vandalism threshold. A high-theft/vandalism zone maybe comprised of an area having a number of theft/vandalism incidentsgreater than or equal to the second theft/vandalism threshold.

The plurality of demand zones, saturation zones, and theft/vandalismzones may overlap. An on-demand electric vehicle may be located in ahigh-demand zone, but the high-demand zone is also a high-saturationzone. In the event an electric vehicle available for rental is locatedin any inefficient use zone (e.g., low-demand zone, a high-saturationzone, or a high-theft/vandalism zone), backend server 112 may update auser interface of an application associated with an on-demand electricvehicle provider that indicates a location of one or more electricvehicles located in an inefficient use zone. A rebalancer via therebalancer's mobile device may view via the applications user interfacecorresponding locations associated with one or more electric vehicleslocated in one or more inefficient use zones. Each electric vehiclelocated in an inefficient use zone may have a corresponding incentive.Examples of incentives include money, credits to use electric vehiclesassociated with the electric vehicle provider, credits to use at a goodsprovider (e.g., retail provider, food provider, etc.), credits to use ata service provider (e.g., free car wash, free house cleaning, etc.),etc.

Backend server 112 may receive a selection of one or more electricvehicles located in a corresponding inefficient use zone. In response tothe selection, backend server 112 may update the user interface suchthat the one or more selected electric vehicles are no longer availablefor one or more other rebalancers to select. Backend server 112 mayreceive an indication that a selected on-demand electric vehicle hasbeen relocated from an inefficient use zone to an efficient use zone(e.g., medium-demand zone, high-demand zone, low-saturation zone,medium-saturation zone, low-theft/vandalism zone, medium-theft/vandalismzone). For example, backend server 112 may receive a picture of therelocated on-demand electric vehicle from a mobile device associatedwith the rebalancer. The picture may include metadata that indicates alocation at which the picture was taken. Backend server may determinethat the on-demand electric vehicle has been relocated to the efficientuse zone based on the metadata. Backend sever 112 may receive from therelocated on-demand vehicle location data that indicates the on-demandelectric vehicle has been relocated to an efficient use zone. Inresponse to the on-demand electric vehicle being re-located to anefficient use zone, backend server 112 may provide the incentiveassociated with the re-located electric vehicle to the rebalancer.

FIG. 2 is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle. In the example shown, process200 may be implemented by a backend server, such as backend server 112,or an electric vehicle, such as electric vehicles 102 a, 102 n.

At 202, a location associated with an on-demand electric vehicle isdynamically determined during a ride to be associated with one or morerestrictions.

The on-demand electric vehicle may be equipped with a location sensor(e.g., GPS). The location sensor may output location data associatedwith the on-demand electric vehicle during a ride of the on-demandelectric vehicle. A processor of the on-demand electric vehicle maydetermine the location of the on-demand electric vehicle based on thelocation data. The location may be determined a plurality of timesduring the ride of the on-demand electric vehicle.

Location data associated with the on-demand electric vehicle may beprovided to a backend server during a ride of the on-demand electricvehicle. In some embodiments, the location data associated with theon-demand electric vehicle is directly provided to the backend servervia a wireless connection of the on-demand electric vehicle. In someembodiments, the location data associated with the on-demand electricvehicle is indirectly provided to the backend server via a wirelessconnection of a mobile device that is coupled to the on-demand electricvehicle.

The backend server may receive the location data associated with theon-demand electric vehicle and determine the location of the on-demandelectric vehicle based on the received location data. The backend servermay receive a plurality of location data and determine a plurality oftimes during the ride a location of the on-demand electric vehicle.

At 204, configuration data is used to enforce the one or morerestrictions with respect to operation of the on-demand electric vehiclein connection with the ride.

A location of an on-demand electric vehicle may be associated with oneor more restrictions. For example, the on-demand electric vehicle may benear or in a restricted area. The on-demand electric vehicle may be inan area subject to one or more speed restrictions. The on-demandelectric vehicle may be in an area subject to one or more weatherrestrictions. The on-demand electric vehicle may be in an area subjectto one or more time-based restrictions.

In the event it is determined that the on-demand electric vehicle'slocation is associated with one or more restrictions, configuration datamay be used to enforce the one or more restrictions with respect tooperation of the on-demand electric vehicle in connection with the ride.The backend server may provide configuration data to the on-demandelectric vehicle to enforce the one or more restrictions with respect tooperation of the on-demand electric vehicle in connection with the ride.In response to receiving the configuration data, the on-demand electricvehicle may apply the one or more restrictions with respect to operationof the on-demand electric vehicle in connection with the ride. Forexample, the configuration data may indicate a maximum speed associatedwith the on-demand electric vehicle for a particular location or an areanear the particular location.

In some embodiments, the configuration data is provided at the start ofthe ride based on an initial location of the on-demand electric vehicle.In some embodiments, the configuration data is provided during the ridebased on a current location of the on-demand electric vehicle. Theon-demand electric vehicle may apply the configuration data uponreceiving the configuration data.

FIG. 3A is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle. In the example shown, process300 may be implemented by a backend server, such as backend server 112.

At 302, an indication of a rental associated with an on-demand electricvehicle is received. A user may rent an on-demand electric vehicle usingan app associated with the on-demand electric vehicle provider that isinstalled on the user's mobile device. In some embodiments, the user mayuse the app to scan a QR code associated with the on-demand electricvehicle to activate a rental. In other embodiments, the user may use theapp to enter a code associated with the on-demand electric vehicle(e.g., a code marked on the on-demand electric vehicle) to activate arental. Upon scanning the QR code associated with the on-demand electricvehicle or entering a correct code associated with the on-demandelectric vehicle, the mobile device associated with the user may send toa backend server the indication of a rental associated with theon-demand electric vehicle.

At 304, a location associated with the rented on-demand electric vehicleis monitored. The location associated with the rented on-demand electricvehicle may be monitored in real-time. Location data may be receivedfrom the rented on-demand electric vehicle, a mobile device associatedwith a user of the rented on-demand electric vehicle, or both. Locationdata may be received on a periodic basis during a rental period of theon-demand electric vehicle (e.g., every half second, every second, everyfive seconds, etc.). The mobile device associated with the user of therented on-demand electric vehicle may include an application associatedwith the on-demand electric vehicle. The application associated with theon-demand electric vehicle may cause the mobile device location dataassociated with mobile device to be provided during a rental period ofthe rented on-demand electric vehicle.

At 306, it is determined whether the monitored location is associatedwith one or more restrictions. The location data from the rentedon-demand electric vehicle, a mobile device associated with a user ofthe rented on-demand electric vehicle, or both, may be used to determinea current location of the rented on-demand electric vehicle.

In some embodiments, the monitored location is associated with arestricted area. A restricted area may correspond to an area, (e.g.,entire city, a college campus, an area affected by inclement weather, anarea associated with a special event, sidewalks, etc.) where operationof an electric vehicle is not permitted. For example, a city, such asBeverly Hills, may restrict the use of electric vehicles within its citylimits. A college or university, such as San Jose State University, mayrestrict the use of an electric vehicle on its campus. A city, such asNew Orleans, may become flooded after a storm. An electric vehicle maybe unable to properly operate in a flooded area (e.g., a road issubmerged). A special event may be going on when the electric vehicle isrented. Areas associated with the special event may prohibit the use ofan electric vehicle. These areas may correspond to areas where anelectric vehicle is allowed, but for the special event. Some areas maybecome restricted areas during certain times of the day (e.g., between12 pm-4 pm, after 6 pm, between dusk and dawn, etc.).

A backend server may maintain a map that includes one or more restrictedareas. The map may include boundary information associated with the oneor more restricted areas (e.g., a geo-fence). For example, the boundaryinformation may include coordinates associated with the perimeter of arestricted area. A backend server may determine whether the locationdata associated with the rented on-demand electric vehicle is near arestricted area within a threshold distance or in a restricted area bycomparing the received location data to the boundary informationassociated with the one or more restricted areas.

A monitored location is associated with a restricted area in the eventthe location data associated with the rented on-demand electric vehicleis near a restricted area within a threshold distance or in a restrictedarea by comparing the received location data to the boundary informationassociated with the one or more restricted areas. A monitored locationis not associated with a restricted area in the event the location dataassociated with the rented on-demand electric vehicle is not near arestricted area within a threshold distance or not in a restricted areaby comparing the received location data to the boundary informationassociated with the one or more restricted areas.

In some embodiments, the monitored location is associated with an areasubject to a speed restriction. A user may ride the electric vehicle atan inappropriate speed for a particular context (e.g., time of day,location, weather, traffic conditions, special events, etc.). Themonitored location may be used to determine if a speed restrictionshould be applied to the rented on-demand electric vehicle. An area maypermit the operation of on-demand electric vehicles, but at speeds lowerthan a capability of the electric vehicle. For example, the defaultmaximum speed of an electric vehicle may be 15 mph. An area may permitthe operation of electric vehicles, but at a maximum speed of 7 mph.

In some embodiments, an area is subject to a speed restriction during aparticular time of day (e.g., (e.g., between 12 pm-4 pm, after 6 pm). Insome embodiments, an area is subject to a speed restriction from local,state, or federal regulations. For example, a local city ordinance maystipulate that the maximum speed for an on-demand electric vehicle on abeach bike path is 8 mph. In some embodiments, an area is subject to aspeed restriction based on weather conditions. For example, the maximumspeed for an on-demand electric vehicle in a particular area while it israining may be 5 mph. In some embodiments, an area is subject to a speedrestriction based on current traffic conditions. For example, an area(e.g., main road) may have a certain amount of cars on it during aparticular time of day (rush hour). The maximum speed for an electricvehicle may be reduced during the particular time of day based ontraffic conditions. This may prevent a number of accidents associatedwith users of electric vehicles since the electric vehicles will betraveling at lower speeds. In some embodiments, an area is subject to aspeed restriction during a special event. For example, an area may hosta street festival. During the hours of the street festival, the maximumspeed for an electric vehicle may be reduced in the area of the streetfestival.

A backend server may maintain a map that includes one or more areassubject to one or more speed restrictions. The map may include boundaryinformation associated with the one or more areas subject to one or morespeed restrictions. For example, the boundary information may includecoordinates associated with the perimeter of an area subject to one ormore speed restrictions. A backend server may determine whether thelocation data associated with the rented on-demand electric vehicle isin an area subject to one or more speed restrictions.

In the event the monitored location is not associated with one or morerestrictions (e.g., not near or within a restricted area or not withinan area subject to one or more speed restrictions), process 300 proceedsto 312. In the event the monitored location is associated with one ormore restrictions (e.g., near or within a restricted area or within anarea subject to a speed restrictions), process 300 proceeds to 308.

At 308, it is determined whether configuration data associated with theone or more determined restrictions has been already provided. In theevent the configuration data associated with the one or more determinedrestrictions has been already provided, process 300 returns to 304. Inthe event the configuration data associated with the one or moredetermined restrictions has not been already provided, process 300proceeds to 310.

At 310, configuration data associated with the one or more determinedrestrictions is provided to the rented on-demand electric vehicle. Insome embodiments, step 310 is implemented to perform some or all of step204 of process 200. The configuration data associated with the one ormore restrictions may reduce a maximum speed associated with the rentedon-demand electric vehicle. In some embodiments, the maximum speedassociated with the rented on-demand electric vehicle is reduced fromthe default maximum speed associated with the rented on-demand electricvehicle to a speed greater than 0 mph. In some embodiments, the maximumspeed associated with the rented on-demand electric vehicle is reducedfrom a reduced maximum speed associated with the rented on-demandelectric vehicle to 0 mph. In some embodiments, the maximum speedassociated with the rented on-demand electric vehicle is reduced fromthe default maximum speed associated with the rented on-demand electricvehicle to 0 mph.

At 312, it is determined if a rental of the rented on-demand electricvehicle has ended. A user associated with the rented on-demand electricvehicle may use the application associated with the on-demand electricvehicle provider to indicate that a rental of the rented on-demandelectric vehicle has ended. In response to the indication, theapplication associated with the on-demand electric vehicle provider maycause the mobile device on which the application is installed to providea notification that the rental has ended to the backend server. In someembodiments, the on-demand electric vehicle includes an interface thatallows a user of the on-demand electric vehicle to indicate that therental has ended. In response to receiving an interaction that indicatesthe rental has ended, the on-demand electric vehicle may be configuredto provide a notification that the rental has ended to the backendserver.

In the event it is determined that the rental of the rented on-demandelectric vehicle has ended, process 300 proceeds to 314. In the event itis determined that the rental of the rented on-demand electric vehiclehas not ended, process 300 returns to 304.

At 314, a database is updated. The database may be updated to indicatethe rented on-demand electric vehicle is now available for rental. Thedatabase may be updated to indicate the rented on-demand electricvehicle is now available for charging. The database may be updated toindicate the rented on-demand electric vehicle is now available forrebalancing. The database may indicate that the rented on-demandelectric vehicle is in an up-right position.

The backend server may provide a user interface in the applicationassociated with the on-demand electric vehicle provider. The userinterface may be updated based on the updated database information. Forexample, a potential rider may see via the application user interfacethat the rented on-demand electric vehicle is now available for rental.A potential charger may see via the application user interface that therented on-demand electric vehicle is now available for charging. Apotential rebalancer may see via the application user interface that therented on-demand electric vehicle is now available for re-location.

FIG. 3B is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle. In the example shown, process350 may be implemented by an electric vehicle, such as electric vehicles112 a, 112 n. The maximum speed of the on-demand electric vehicle maydynamically change based on a geo-location of the on-demand electricvehicle.

At 352, location data associated with a rented on-demand electricvehicle is provided. The location data may be provided to a backendserver, such as backend server 112. The location data may be providedfrom the rented on-demand electric vehicle, a mobile device associatedwith a user of the rented on-demand electric vehicle, or both. Locationdata may be provided on a periodic basis during a rental period of theon-demand electric vehicle (e.g., every half second, every second, everyfive seconds, etc.). The mobile device associated with the user of therented on-demand electric vehicle may include an application associatedwith the on-demand electric vehicle. The application associated with theon-demand electric vehicle may cause location data associated withmobile device to be provided during a rental period of the rentedon-demand electric vehicle.

At 354, configuration data associated with one or more restrictions isreceived. The one or more restrictions may be associated with arestricted area. The one or more restrictions may be associated with anarea subject to a speed restriction. A backend server that received theprovided location data may determine that the rented on-demand electricvehicle is near or in a restricted area. The backend server may provideconfiguration data associated with a restricted area. The configurationdata may include a maximum speed configuration data for the rentedon-demand electric vehicle when the rented on-demand electric vehicle isnear the restricted area within a threshold distance. The configurationdata may include a maximum speed configuration data (e.g., 0 mph) forthe rented on-demand electric vehicle when the rented on-demand electricvehicle is in the restricted area.

A backend server that received the provided location data may determinethat the rented on-demand electric vehicle in an area subject to a speedrestriction. The backend server may provide configuration dataassociated with the area subject to a speed restriction. Theconfiguration data may include a maximum speed configuration data forthe rented on-demand electric vehicle for the provided location.

At 356, a configuration of the rented on-demand electric vehicle isupdated based on the received configuration data. In some embodiments,step 356 is implemented to perform some or all of step 204 of process200.

In the event the provided location data indicates that the rentedon-demand electric vehicle is near a restricted area within a thresholddistance, the received configuration data may reduce the maximum speedassociated with the rented on-demand electric vehicle. A processor ofthe rented on-demand electric vehicle may reduce the maximum speedassociated with the on-demand electric vehicle by reducing the maximumamount of voltage, current, or power given to an electric motor of theon-demand electric vehicle.

In the event the provided location data indicates that the rentedon-demand electric vehicle is in a restricted area, the receivedconfiguration data may reduce the maximum speed associated with therented on-demand electric vehicle. For example, the maximum speed of theon-demand electric vehicle may be reduced to 0 mph, which causes theuser of the on-demand electric vehicle to get off the on-demand electricvehicle and walk the on-demand electric vehicle out of the restrictedarea. The processor of the on-demand electric vehicle may prevent thepower source of the on-demand electric vehicle from providing voltage,current, or power given to the electric motor of the on-demand electricvehicle.

In the event the provided location data indicates that the rentedon-demand electric vehicle is in an area subject to a speed restriction,the received configuration data may reduce the maximum speed associatedwith the rented on-demand electric vehicle. A processor of the rentedon-demand electric vehicle may reduce the maximum speed associated withthe on-demand electric vehicle by reducing the maximum amount ofvoltage, current, or power given to an electric motor of the on-demandelectric vehicle.

FIG. 4A is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle. In the example shown, process400 may be implemented by a backed server, such as backend server 112.

At 402, an indication of a rental associated with an on-demand electricvehicle is received. A user may rent an on-demand electric vehicle usingan app associated with the on-demand electric vehicle provider that isinstalled on the user's mobile device. In some embodiments, the user mayuse the app to scan a QR code associated with the on-demand electricvehicle to activate a rental. In other embodiments, the user may use theapp to enter a code associated with the on-demand electric vehicle(e.g., a code marked on the on-demand electric vehicle) to activate arental. Upon scanning the QR code associated with the on-demand electricvehicle or entering a correct code associated with the on-demandelectric vehicle, the mobile device associated with the user may send toa backend server the indication of a rental associated with theon-demand electric vehicle.

At 404, an initial location associated with the rented on-demandelectric vehicle is determined. The on-demand electric vehicle mayinclude a GPS device that provides location data. In some embodiments,location data associated with the rented on-demand electric vehicle isdirectly received from the on-demand electric vehicle. In someembodiments, location data associated with the rented on-demand electricvehicle is indirectly received from the on-demand electric vehicle viathe user's mobile device. For example, location data associated with therented on-demand electric vehicle is received from the user's mobiledevice. The mobile device associated with the user of the rentedon-demand electric vehicle may include an application associated withthe on-demand electric vehicle. The application associated with theon-demand electric vehicle may cause location data associated withmobile device to be provided during a rental period of the rentedon-demand electric vehicle.

Upon receiving the location data, the backend server may determine thelocation associated with the rented on-demand electric vehicle. Thelocation data from the rented on-demand electric vehicle, a mobiledevice associated with a user of the rented on-demand electric vehicle,or both, may be used to determine the location of the rented on-demandelectric vehicle.

At 406, it is determined whether the rented on-demand electric vehicleis associated with one or more restrictions based on the locationassociated with the rented on-demand electric vehicle.

An on-demand electric vehicle includes one or more batteries that powerthe electric vehicle. A user may rent an on-demand electric vehicle anduse the on-demand electric vehicle until the on-demand electric vehicleruns out of power. The on-demand electric vehicle has a particularamount of power remaining at the time of rental. The particular amountof power remaining corresponds to a particular distance. For example, anon-demand electric vehicle with a battery at 100% charge may travel adistance of approximately 15 miles without recharging. An on-demandelectric vehicle with a battery at 50% charge may travel a distance ofapproximately 7 miles without recharging. An on-demand electric vehiclewith a battery at 25% charge may travel a distance of approximately 3miles without recharging. A rented on-demand electric vehicle isassociated with a travel radius. The travel radius corresponds to apotential distance that the on-demand electric vehicle may travel if theon-demand electric vehicle were to travel in a straight line until theone or more batteries of the on-demand electric vehicle are no longerable to power the on-demand electric vehicle.

A potential circle of travel may be generated to determine the potentialareas to which the rented on-demand electric vehicle may travel. Thepotential circle of travel is specific to each on-demand electricvehicle and is based on the initial location of the rented on-demandelectric vehicle and the amount of charge remaining associated with therented on-demand electric vehicle. In some embodiments, the potentialcircle of travel is an imperfect circle when considering other factorsthat affect the potential range of an on-demand electric vehicle, suchas elevation gain/loss, road conditions, etc.

The potential areas may be associated with one or more restrictions. Insome embodiments, the potential areas include one or more restrictedareas. A restricted area may correspond to an entire city, a collegecampus, an area affected by inclement weather, an area associated with aspecial event. For example, a city, such as Beverly Hills, may restrictthe use of on-demand electric vehicles within its city limits. A collegeor university, such as San Jose State University, may restrict the useof an on-demand electric vehicle on its campus. A city, such as NewOrleans, may become flooded after a storm. An electric vehicle may beunable to properly operate in a flooded area (e.g., a road issubmerged). A special event may be going on when the on-demand electricvehicle is rented. Areas associated with the special event may prohibitthe use of an on-demand electric vehicle. These areas may correspond toareas where an on-demand electric vehicle is allowed, but for thespecial event.

In some embodiments, the potential areas are associated with one or moreareas subject to speed restrictions. A user may ride the electricvehicle at an inappropriate speed for a particular context (e.g., timeof day, location, weather, traffic conditions, special events, etc.).The monitored location may be used to determine if a speed restrictionshould be applied to the rented on-demand electric vehicle. An area maypermit the operation of on-demand electric vehicles, but at speeds lowerthan a capability of the on-demand electric vehicle. For example, thedefault maximum speed of an on-demand electric vehicle may be 15 mph. Anarea may permit the operation of on-demand electric vehicles, but at amaximum speed of 7 mph.

In some embodiments, an area is subject to a speed restriction during aparticular time of day (e.g., (e.g., between 12 pm-4 pm, after 6 pm). Insome embodiments, an area is subject to a speed restriction from local,state, or federal regulations. For example, a local city ordinance maystipulate that the maximum speed for an on-demand electric vehicle on abeach bike path is 8 mph. In some embodiments, an area is subject to aspeed restriction based on weather conditions. For example, the maximumspeed for an on-demand electric vehicle in a particular area while it israining may be 5 mph. In some embodiments, an area is subject to a speedrestriction based on current traffic conditions. For example, an area(e.g., main road) may have a certain amount of cars on it during aparticular time of day (rush hour). The maximum speed for an on-demandelectric vehicle may be reduced during the particular time of day basedon traffic conditions. This may prevent a number of accidents associatedwith users of on-demand electric vehicles since the on-demand electricvehicles will be traveling at lower speeds. In some embodiments, an areais subject to a speed restriction during a special event. For example,an area may host a street festival. During the hours of the streetfestival, the maximum speed for an on-demand electric vehicle may bereduced in the area of the street festival.

A backend server may maintain a map that includes one or more areassubject to one or more speed restrictions. The map may include boundaryinformation associated with the one or more areas subject to one or morespeed restrictions. For example, the boundary information may includecoordinates associated with the perimeter of an area subject to one ormore speed restrictions. A backend server may determine whether thelocation data associated with the rented on-demand electric vehicle isin an area subject to one or more speed restrictions.

In the event the rented on-demand electric vehicle is associated withone or more determined restrictions, process 400 proceeds to 408. Arented on-demand electric vehicle is associated with one or moredetermined restrictions in the event at least a portion of a restrictedarea or a portion of an area subject to a speed restriction is includedin the potential circle of travel associated with the rented on-demandelectric vehicle.

In the event the rented on-demand electric vehicle is not associatedwith one or more restricted areas, process 400 proceeds to 410. A rentedon-demand electric vehicle is not associated with one or more determinedrestrictions in the event at least a portion of a restricted area or aportion of an area subject to a speed restriction is not included in thepotential circle of travel associated with the rented on-demand electricvehicle.

At 408, configuration data associated with the one or more determinedrestrictions is provided to the rented on-demand electric vehicle. Insome embodiments, step 408 is implemented to perform some or all of step204 of process 200. The configuration data associated with the one ormore restrictions may reduce a maximum speed associated with the rentedon-demand electric vehicle. In some embodiments, the maximum speedassociated with the rented on-demand electric vehicle is reduced fromthe default maximum speed associated with the rented on-demand electricvehicle to a speed greater than 0 mph. In some embodiments, the maximumspeed associated with the rented on-demand electric vehicle is reducedfrom a reduced maximum speed associated with the rented on-demandelectric vehicle to 0 mph. In some embodiments, the maximum speedassociated with the rented on-demand electric vehicle is reduced fromthe default maximum speed associated with the rented on-demand electricvehicle to 0 mph.

The configuration data associated with the one or more determinedrestrictions areas may include boundary information that indicates theboundaries associated with the one or more determined restricted areas.The power source (e.g., one or more batteries) of the rented on-demandelectric vehicle may be prevented from providing power to the electricmotor of the rented on-demand electric vehicle while the rentedon-demand electric vehicle is located in a restricted area.

The configuration data associated with the one or more determinedrestricted areas may include corresponding threshold distanceinformation with the one or more determined restricted areas. Thresholddistance information may indicate a distance from a boundary associatedwith a restricted area at which a maximum speed of a rented on-demandelectric vehicle is reduced. The maximum speed of the rented on-demandelectric vehicle may decrease as the rented on-demand electric vehiclegets closer to the boundary associated with the restricted area. Forexample, the maximum speed of the rented on-demand electric vehicle maybe 15 mph. The maximum speed may be reduced from 15 mph to 8 mph whenthe rented on-demand electric vehicle is within the threshold distance(e.g., 50 feet) of a restricted area. The maximum speed may be furtherreduced from 8 mph to 3 mph as the rented on-demand electric vehiclegets closer to the boundary of the restricted area (e.g., 10 feet). Thismay prevent a user of the rented on-demand electric vehicle from fallingoff the electric vehicle when the electric vehicle enters the restrictedarea.

The configuration data associated with the one or more determinedrestricted areas may include time information that indicates whenrestrictions associated with the one or more determined restricted areasare no longer applicable. For example, a street festival may be going onwhen an on-demand electric vehicle is rented. The on-demand electricvehicle may have enough charge to reach the area associated with thestreet festival. However, the street festival may end during a rentalperiod associated with the rented on-demand electric vehicle. In theevent the rented on-demand electric vehicle enters the area associatedwith the street festival after the street festival ends, therestrictions of the area associated with the street festival may notapply anymore, and the rented on-demand electric vehicle should be ableto enter the area associated with the street festival.

The configuration data associated with the one or more determinedrestrictions areas may include boundary information that indicates theboundaries associated with the one or more determined areas subject tospeed restrictions. The amount of power provided by the power source(e.g., one or more batteries) of the rented on-demand electric vehiclemay be reduced while the rented on-demand electric vehicle is located inan area subject to a speed restriction.

At 410, a configuration associated with the rented on-demand electricvehicle is maintained. By default, a rented on-demand electric vehiclemay not be associated with any restricted areas. A user associated withthe rented on-demand electric vehicle may be able to ride the rentedon-demand electric vehicle to any location without any speedrestrictions, provided the rented on-demand electric vehicle still hasenough charge to power the rented on-demand electric vehicle.

FIG. 4B is a flow chart illustrating an embodiment of a process toconfigure an on-demand electric vehicle. In the example shown, process450 may be implemented by an on-demand electric vehicle, such aselectric vehicles 102 a, 102 n. In some embodiments, process 450 isimplemented to perform some or all of step 204 of process 200.

At 452, configuration data associated with one or more restrictions isreceived. As discussed above, a rented on-demand electric vehicle may beassociated with one or more restricted areas based on a chargeassociated with the rented on-demand electric vehicle. The configurationdata associated with the one or more determined restricted areas mayinclude corresponding threshold distance information with the one ormore determined restricted areas. In some embodiments, the configurationdata associated with the one or more determined restricted areas mayinclude corresponding threshold distance information with the one ormore determined restricted areas. The configuration data associated withthe one or more determined restricted areas may include time informationthat indicates when restrictions associated with the one or moredetermined restricted areas are no longer applicable.

At 454, a configuration of a rented on-demand electric vehicle isupdated based on the received configuration data. The on-demand electricvehicle may include a computer system, such as computer system 108. Thecomputer system may include a memory and/or storage device that isconfigured to store configuration data associated with the on-demandelectric vehicle. The on-demand electric vehicle may include a locationdevice, such as a GPS. The data associated with the location device maybe used by a processor of the on-demand electric vehicle to determine alocation of the on-demand electric vehicle. The stored configurationdata may be used by the on-demand electric vehicle's processor todetermine how to control the on-demand electric vehicle.

At 456, a location associated with the on-demand electric vehicle ismonitored. The received configuration data may include data associatedwith one or more restricted areas or one or more areas subject to one ormore speed restrictions. For example, the data associated with one ormore restricted areas may include coordinates associated with therestricted area. During a rental period of an on-demand electricvehicle, the processor may compare the coordinates associated with therestricted area to the location data provided by the location device todetermine whether the on-demand is near or located in a restricted area.

At 458, it is determined whether the maximum speed of the on-demandelectric vehicle needs to be reduced. In some embodiments, the maximumspeed of the on-demand electric vehicle needs to be reduced in the eventthe on-demand electric vehicle is located in an area subject to a speedreduction. In some embodiments, the maximum speed of the on-demandelectric vehicle needs to be reduced in the event the on-demand electricvehicle is located near a restricted area within a threshold distance.

The processor of the on-demand electric vehicle may compare the locationdata provided by the location device to the boundary coordinatesincluded in the received configuration data to whether to reduce amaximum speed of the on-demand electric vehicle. In the event it isdetermined that the on-demand electric vehicle is near one of the one ormore restricted areas within a threshold distance or in an area subjectto a speed restriction, process 450 proceeds to 460. In the event it isdetermined that the on-demand electric vehicle is not near one of theone or more restricted areas within a threshold distance or in an areasubject to a speed restriction, process 450 proceeds to 468.

At 460, a warning that indicates the on-demand electric vehicle isapproaching a restricted area is provided. The on-demand electricvehicle may include a display and the warning may be displayed on thedisplay. In some embodiments, the on-demand electric vehicle may includeone or more lights and the one or more lights may flash as a warning tothe user. In some embodiments, the processor of the on-demand electricvehicle is coupled to a mobile device associated with a user of theon-demand electric vehicle. The warning may be provided to the mobiledevice associated with the user. In some embodiments, the warning is anaudible warning. In some embodiments, the on-demand electric vehicleincludes a projection device and the warning is projected onto theground via the projection device. Step 460 may be optional.

At 462, a speed reduction of the on-demand electric vehicle is caused. Aprocessor of the on-demand electric vehicle may reduce a maximum speedassociated with the on-demand electric vehicle while the on-demandelectric vehicle is located within a threshold distance of a boundary ofa restricted area or in an area subject to a speed restriction. Forexample, the processor of the on-demand electric vehicle may reduce themaximum speed associated with the on-demand electric vehicle by reducingthe maximum amount of voltage, current, or power given to an electricmotor of the on-demand electric vehicle.

At 464, it is determined whether the on-demand electric vehicle is inone of the one or more restricted areas. The on-demand electric vehiclemay be determine to be in a restricted area based on the location dataprovided by a location device of the on-demand electric vehicle. Aprocessor of the on-demand electric vehicle may compare the locationdata with coordinate information associated with the boundary of arestricted area. In the event it is determined that the on-demandelectric vehicle is in one of the one or more restricted areas, process450 proceeds to 466. In the event it is determined that the on-demandelectric vehicle is not in one of the one or more restricted areas,process 450 proceeds to 468.

At 466, a warning that indicates the on-demand electric vehicle is in arestricted area is provided. The on-demand electric vehicle may includea display and the warning may be displayed on the display. In someembodiments, the on-demand electric vehicle may include one or morelights and the one or more lights may flash as a warning to the user. Insome embodiments, the processor of the on-demand electric vehicle iscoupled to a mobile device associated with a user of the on-demandelectric vehicle. The warning may be provided to the mobile deviceassociated with the user. In some embodiments, the warning is an audiblewarning. In some embodiments, the on-demand electric vehicle includes aprojection device and the warning is projected onto the ground via theprojection device. Step 466 may be optional.

At 468, an operation of the on-demand electric vehicle is restricted inthe restricted area. For example, the maximum speed of the on-demandelectric vehicle may be reduced to 0 mph, which causes the user of theon-demand electric vehicle to get off the on-demand electric vehicle andwalk the on-demand electric vehicle out of the restricted area. Theprocessor of the on-demand electric vehicle may prevent the power sourceof the on-demand electric vehicle from providing voltage, current, orpower given to the electric motor of the on-demand electric vehicle.

At 470, operation of the on-demand electric vehicle is maintained. Theon-demand electric vehicle may be able to operate until a user of theon-demand electric vehicle has ended the user's rental.

At 472, it is determined if a rental of the rented on-demand electricvehicle has ended. A user associated with the rented on-demand electricvehicle may use the application associated with the on-demand electricvehicle provider to indicate that a rental of the rented on-demandelectric vehicle has ended. In response to the indication, theapplication associated with the on-demand electric vehicle provider maycause the mobile device on which the application is installed to providea notification that the rental has ended to the backend server. In someembodiments, the on-demand electric vehicle includes an interface thatallows a user of the on-demand electric vehicle to indicate that therental has ended. In response to receiving an interaction that indicatesthe rental has ended, the on-demand electric vehicle may be configuredto provide a notification that the rental has ended to the backendserver.

In the event it is determined that the rental of the rented on-demandelectric vehicle has ended, process 450 proceeds to 474. In the event itis determined that the rental of the rented on-demand electric vehiclehas not ended, process 450 returns to 456.

At 474, a database is updated. The database may be updated to indicatethe rented on-demand electric vehicle is now available for rental. Thedatabase may be updated to indicate the rented on-demand electricvehicle is now available for charging. The database may be updated toindicate the rented on-demand electric vehicle is now available forrebalancing.

The backend server may provide a user interface in the applicationassociated with the on-demand electric vehicle provider. The userinterface may be updated based on the updated database information. Forexample, a potential rider may see via the application user interfacethat the rented on-demand electric vehicle is now available for rental.A potential charger may see via the application user interface that therented on-demand electric vehicle is now available for charging. Apotential rebalancer may see via the application user interface that therented on-demand electric vehicle is now available for re-location.

FIG. 5A is a flow chart illustrating an embodiment of a process tomaintain on-demand electric vehicles in an up-right position. In theexample shown, process 500 may be implemented by an electric vehicle,such as electric scooter 102. After a user has finished a rental of theelectric vehicle, the electric vehicle may be placed in an uprightposition. The user may provide photographic evidence to an on-demandelectric vehicle provider to demonstrate that the on-demand electricvehicle was left in an up-right position. At some moment in time later,the electric vehicle may be tipped over (either accidentally oron-purpose). The electric vehicle may remain in a fallen position untilsomeone fixes the position of the fallen electric vehicle (i.e., placethe fallen electric vehicle in an upright position). Fallen electricvehicles may be viewed as a nuisance because they may be blockingsidewalks, pathways, or doorways.

At 502, it is determined that an on-demand electric vehicle has fallen.The on-demand electric vehicle may include an orientation sensor, a tiltsensor, and/or an acceleration sensor. In some embodiments, theorientation sensor outputs a value that indicates that the on-demandelectric vehicle is no longer in an up-right position. In someembodiments, the tilt sensor outputs a value that indicates that theon-demand electric vehicle is no longer in an up-right position. In someembodiments, the acceleration sensor outputs a value that indicates thatthe on-demand electric vehicle is no longer in an up-right position. Forexample, the acceleration sensor may output one or more values while theon-demand electric vehicle is transitioning from an up-right position toa fallen position.

At 504, an indication that the on-demand electric vehicle has fallen isprovided. The indication may be provided from the on-demand electricvehicle to a backend server (e.g., backend serer 112) that is configuredto monitor the up-right status associated with a fleet of on-demandelectric vehicles. In some embodiments, the indication includes anoutput of an orientation sensor. In some embodiments, the indicationincludes an output of the acceleration sensor. In some embodiments, theindication includes an output of the tilt sensor. In some embodiments,the indication includes a notification that the on-demand electricvehicle is no longer in an up-right position.

In response to the indication, the backend server may update a userinterface that indicates a location of one or more fallen electricvehicles. A fixer via the fixer's mobile device may view correspondinglocations associated with one or more fallen electric vehicles. Eachfallen electric vehicle may have a corresponding incentive. Examples ofincentives include money, credits to use electric vehicles associatedwith the electric vehicle provider, credits to use at a goods provider(e.g., retail provider, food provider, etc.), credits to use at aservice provider (e.g., free car wash, free house cleaning, etc.), etc.A fixer may select to fix the fallen on-demand electric vehicle.

At 506, it is determined that the on-demand electric vehicle is in anupright positon is determined. For example, a fixer may have correctedan orientation of an electric vehicle from a fallen position to anup-right position. In some embodiments, the orientation sensor outputs avalue that indicates that the on-demand electric vehicle is in anup-right position. In some embodiments, the tilt sensor outputs a valuethat indicates that the on-demand electric vehicle is in an up-rightposition. In some embodiments, the acceleration sensor outputs a valuethat indicates that on-demand electric vehicle is in an up-rightposition. For example, the acceleration sensor may output one or morevalues while the on-demand electric vehicle is transitioning from afallen position to an up-right position.

At 508, an indication that the electric vehicle is in an uprightposition is provided. The indication may be provided from the on-demandelectric vehicle to a backend server that is configured to monitor theup-right status associated with a fleet of on-demand electric vehicles.In some embodiments, the indication includes an output of an orientationsensor. In some embodiments, the indication includes an output of theacceleration sensor. In some embodiments, the indication includes anoutput of the tilt sensor. In some embodiments, the indication includesa notification that the on-demand electric vehicle is in an up-rightposition. In response to the indication, the backend server may provideto the fixer an incentive associated with the fallen on-demand electricvehicle.

FIG. 5B is a flow chart illustrating an embodiment of a process tomaintain on-demand electric vehicles in an up-right position. In theexample shown, process 540 may be implemented by a backed server, suchas backend server 112.

At 542, an indication that an on-demand electric vehicle has fallen isreceived. The indication may be received from the on-demand electricvehicle. An on-demand electric vehicle may include one or more sensors.One of the sensors may be an orientation sensor. The indication mayinclude an output of the orientation sensor. The orientation sensoroutput may include data that indicates that the on-demand electricvehicle is no longer in an upright position. One of the sensors may be atilt sensor. The indication may include an output of the tilt sensor.The tilt sensor output may include data that indicates that theon-demand electric vehicle is no longer in an upright position. One ofthe sensors may be an acceleration sensor. The indication may include anoutput of the acceleration sensor. The acceleration sensor output mayinclude data that indicates that the on-demand electric vehicle is nolonger in an upright position.

In some embodiments, the on-demand electric vehicle has determined thatit is no longer in an upright positon based on data from the one or moresensors. The on-demand electric vehicle may provide an indication thatnotifies the backend server that the on-demand electric vehicle is nolonger in an upright position. The indication may include location dataassociated with the on-demand electric vehicle.

At 544, information indicating a location of one or more on-demandelectric vehicles that have fallen is provided via a user interface. Thebacked server may update a user interface that indicates a location ofone or more fallen electric vehicles. A fixer via the fixer's mobiledevice may view corresponding locations associated with one or morefallen electric vehicles. Each fallen electric vehicle may have acorresponding incentive. Examples of incentives include money, creditsto use electric vehicles associated with the electric vehicle provider,credits to use at a goods provider (e.g., retail provider, foodprovider, etc.), credits to use at a service provider (e.g., free carwash, free house cleaning, etc.), etc. The information may be providedon a map or a list.

At 546, a selection of the on-demand electric vehicle is received. Afixer may select the on-demand electric vehicle via a user interface ofthe application associated with the on-demand electric vehicle providerthat is installed on the fixer's mobile device.

At 548, the user interface is updated to indicate that the on-demandelectric vehicle has been selected. The user interface may display aplurality of fallen on-demand electric vehicles. The user interface maybe updated such that the selected on-demand electric vehicle is nolonger shown. This may prevent one or more other fixers from selectingthe selected fallen on-demand electric vehicle.

At 550, an indication that the fallen on-demand electric vehicle is inan up-right position is received. The indication may be received fromthe on-demand electric vehicle. In some embodiments, the indicationincludes an output of an orientation sensor. In some embodiments, theindication includes an output of the acceleration sensor. In someembodiments, the indication includes an output of the tilt sensor. Insome embodiments, the indication includes a notification that theon-demand electric vehicle is in an up-right position.

In some embodiments, the indication is received from an applicationassociated with the on-demand electric vehicle provider. The applicationmay include a feature that allows the fixer to use a camera of themobile device to capture an image of the fallen electric vehicle in anupright position. The image may be sent from the fixer's mobile deviceto the backend server.

At 552, an incentive corresponding to the fallen on-demand electricvehicle is provided to the fixer.

FIG. 5C is a flow chart illustrating an embodiment of a process tomaintain on-demand electric vehicles in an up-right position. In theexample shown, process 570 may be implemented by a backed server, suchas backend server 112.

At 572, a plurality of indications that a plurality of on-demandelectric vehicles have fallen are received. An on-demand electricvehicle may include one or more sensors. One of the sensors may be anorientation sensor. The indication may include an output of theorientation sensor. The orientation sensor output may include data thatindicates that the on-demand electric vehicle is no longer in an uprightposition. One of the sensors may be a tilt sensor. The indication mayinclude an output of the tilt sensor. The tilt sensor output may includedata that indicates that the on-demand electric vehicle is no longer inan upright position. One of the sensors may be an acceleration sensor.The indication may include an output of the acceleration sensor. Theacceleration sensor output may include data that indicates that theon-demand electric vehicle is no longer in an upright position.

In some embodiments, the on-demand electric vehicle has determined thatit is no longer in an upright positon based on data from the one or moresensors. The on-demand electric vehicle may provide an indication thatnotifies the backend server that the on-demand electric vehicle is nolonger in an upright position. The indication may include location dataassociated with the on-demand electric vehicle.

At 574, a route is determined based on corresponding locationsassociated with the plurality of on-demand electric vehicles that havefallen. A fixer may have selected the plurality of on-demand electricvehicles. In other embodiments, a fixer (e.g., an employee of theon-demand electric vehicle provider) is assigned to fix an orientationof the plurality of on-demand electric vehicles. The route may indicatean order in which the plurality of on-demand electric vehicles are to beserviced.

At 576, route information is provided via a user interface to a fixer.An application associated with the on-demand electric vehicle providermay provide a user interface that indicates a location of a plurality offallen on-demand electric vehicles. The route information may beprovided via the application associated with the on-demand electricvehicle provider.

At 578, indications that the fallen on-demand electric vehicles are inan up-right position are received. Corresponding indications may bereceived from each of the plurality of fallen on-demand electricvehicles. In some embodiments, an indication includes an output of anorientation sensor of a fallen on-demand electric vehicle. In someembodiments, the indication includes an output of a tilt sensor of afallen on-demand electric vehicle. In some embodiments, the indicationincludes an output of the acceleration sensor of a fallen on-demandelectric vehicle. In some embodiments, the indication includes anotification that the on-demand electric vehicle is in an up-rightposition.

In some embodiments, the indication is received from an applicationassociated with the on-demand electric vehicle provider. The applicationmay include a feature that allows the fixer to use a camera of themobile device to capture an image of the fallen electric vehicle in anupright position. The image may be sent from the fixer's mobile deviceto the backend server.

At 580, incentives corresponding to the one or more fallen on-demandelectric vehicles are provided to the user.

FIG. 6A is a flow chart illustrating an embodiment of a process torebalance a plurality of on-demand electric vehicles. In the exampleshown, process 600 may be implemented by a backed server, such asbackend server 112. A backend server may maintain a map of on-demandelectric vehicles included in a fleet of on-demand electric vehicles.The map may be updated when location data is received from any of thevehicles included in the fleet.

On-demand electric vehicles may not be tied to a particular dockingstation. This may allow a user to leave an on-demand electric vehicle atany location at the end of a rental. The location may be a sub-optimallocation and may lead to an inefficient use of the on-demand electricvehicle because the on-demand electric vehicle may remain un-used untilit is picked up and relocated to another location.

At 602, location data associated with a plurality of on-demand electricvehicles is received. When a user associated with an on-demand electricvehicle ends a rental, a notification may be provided to the backendserver. The notification may include location data associated with theon-demand electric vehicle. The backend server may store the locationdata associated with an on-demand electric vehicle. The backend servermay store the location data associated with plurality of on-demandelectric vehicles available for rental.

At 604, the received location data is compared with a plurality ofzones. The backend server may partition a map into a plurality of zonesand may maintain the partitioned map. The map may be updated based onadditional rental data associated with a fleet of electric vehicles. Theplurality of zones may comprise one or more low-demand zones, one ormore medium-demand zones, and one or more high-demand zones. Alow-demand zone may be comprised of an area having a frequency of usersbelow a first demand threshold. A medium-demand zone may be comprised ofan area having a frequency of users greater than or equal to the firstdemand threshold and less than a second demand threshold. A high-demandzone may be comprised of an area having a frequency of users greaterthan or equal to the second demand threshold.

The plurality of zones may comprise one or more low-saturation zones,one or more medium-saturation zones, and one or more high-saturationzones. A low-saturation zone may be comprised of an area having a numberof electric vehicles available for rental below a first saturationthreshold. A medium-saturation zone may be comprised of an area having anumber of electric vehicles available for rental greater than or equalto the first saturation threshold and less than a second saturationthreshold. A high-saturation zone may be comprised of an area having anumber of electric vehicles available for rental greater than or equalto the second saturation threshold.

The plurality of zones may comprise one or more low theft/vandalismzones, one or more medium theft/vandalism zones, and one or more hightheft/vandalism zones. A low-theft/vandalism zone may be comprised of anarea having a number of theft/vandalism incidents below a firsttheft/vandalism threshold. A medium-theft/vandalism zone may becomprised of an area having a number of theft/vandalism incidentsgreater than or equal to the first theft/vandalism threshold and lessthan a second theft/vandalism threshold. A high-theft/vandalism zone maybe comprised of an area having a number of theft/vandalism incidentsgreater than or equal to the second theft/vandalism threshold. Theplurality of demand zones, saturation zones, and theft/vandalism zonesmay overlap.

At 606, one or more on-demand electric vehicles that are located in oneor more inefficient use zones are identified. A location of an on-demandelectric vehicle may be compared with a boundary associated with aninefficient use zone. An inefficient use zone may be a low-demand zone,a high-saturation zone, or a high-theft/vandalism zone.

At 608, one or more efficient use zones for the one or more identifiedon-demand electric vehicles is determined. An efficient use zone may bea medium-demand zone, high-demand zone, low-saturation zone,medium-saturation zone, low-theft/vandalism zone, ormedium-theft/vandalism zone. An efficient use zone for the one or moreidentified on-demand electric vehicles may be a zone that is closest tothe inefficient use zone in which the on-demand electric vehicle iscurrently situated. An efficient use zone for the one or more identifiedon-demand electric vehicles may be a zone with the highest probabilityof the one or more identified on-demand electric vehicles being rented.

At 610, information indicating the one or more identified on-demandelectric vehicles are located in a low-demand zone is provided via auser interface of an application associated with an on-demand electricvehicle provider. A rebalancer may have installed on the rebalancer'smobile device, an application associated with the on-demand electricvehicle provider. The application may provide a user interface thatindicates corresponding locations of the one or more identifiedon-demand electric vehicles. The information may include thecorresponding locations and corresponding incentives.

At 612, a selection of at least one of the one or more identifiedon-demand electric vehicles that are located in an inefficient use zoneis received via the user interface of the application associated withthe on-demand electric vehicle provider.

At 614, information indicating corresponding locations within one ormore efficient use zones for the one or more selected on-demand electricvehicles is provided via the user interface of the applicationassociated with the on-demand electric vehicle provider.

At 616, an indication that the one or more selected on-demand electricvehicles are located at the corresponding locations is received. In someembodiments, the indication is received from an application associatedwith the on-demand electric vehicle provider. The application mayinclude a feature that allows the rebalancer to use a camera of themobile device to capture an image of the re-located electric vehicle atthe new location. The image may be sent from the rebalancer's mobiledevice to the backend server. The image may include metadata thatindicates a location at which the image was taken. In some embodiments,an on-demand electric vehicle is configured to periodically providelocation data to the backend server. In some embodiments, theapplication is configured to access location data of the mobile deviceon which the application is installed and to provide the accessedlocation data.

At 618, corresponding incentives associated with the one or moreselected on-demand electric vehicles are provided to the rebalancer.

FIG. 6B is a flow chart illustrating an embodiment of a process torebalance a plurality of on-demand electric vehicles. In the exampleshown, process 550 may be implemented by an application installed on amobile device, such as an application installed on mobile devices 108 a,108 n.

At 652, information indicating that one or more identified on-demandelectric vehicles are located in an inefficient use zone is received ata user interface of an application associated with an on-demand electricvehicle provider. The information may include the correspondinglocations and corresponding incentives.

At 654, at least one of the one or more identified on-demand electricvehicles is selected via the user interface of an application associatedwith an on-demand electric vehicle provider.

At 656, information indicating corresponding locations within one ormore efficient use zones for the one or more selected on-demand electricvehicles is received via the user interface of an application associatedwith an on-demand electric vehicle provider.

At 658, an indication that the one or more selected on-demand electricvehicles are located at the corresponding locations is provided. Theapplication may include a feature that allows the rebalancer to use acamera of the mobile device to capture an image of the relocatedelectric vehicle. The image may be sent from the rebalancer's mobiledevice to the backend server. The image may include metadata thatindicates a location at which the image was taken. In some embodiments,an on-demand electric vehicle is configured to periodically providelocation data to the backend server. In some embodiments, theapplication is configured to access location data of the mobile deviceon which the application is installed and to provide the accessedlocation data.

At 660, corresponding incentives associated with the one or moreselected on-demand electric vehicles are received by the rebalancer. Forexample, an indication may be received via the application userinterface that funds in the amount of the incentive have been creditedand/or paid to the rebalancer.

FIG. 7 is a functional diagram illustrating a computer system inaccordance with some embodiments. Computing system 700 may beimplemented as a computer system, such as computer system 108 a, 108 n.Computer system 700, which includes various subsystems as describedbelow, includes at least one microprocessor subsystem, also referred toas a processor or a central processing unit (“CPU”) 702. For example,processor 702 can be implemented by a single-chip processor or bymultiple cores and/or processors. In some embodiments, processor 702 isa general purpose digital processor that controls the operation of thecomputer system 700. Using instructions retrieved from memory 710, theprocessor 702 controls the reception and manipulation of input data, andthe output and display of data on output devices, for example display718.

Processor 702 is coupled bi-directionally with memory 710, which caninclude a first primary storage, typically a random access memory(“RAM”), and a second primary storage area, typically a read-only memory(“ROM”). Configuration data associated with an on-demand electricvehicle may be stored in memory 710, removable mass storage 712, orfixed mass storage 720. As is well known in the art, primary storage canbe used as a general storage area and as scratch-pad memory, and canalso be used to store input data and processed data. Primary storage canalso store programming instructions and data, in the form of dataobjects and text objects, in addition to other data and instructions forprocesses operating on processor 702. Also as is well known in the art,primary storage typically includes basic operating instructions, programcode, data, and objects used by the processor 702 to perform itsfunctions, for example programmed instructions. For example, primarystorage devices 710 can include any suitable computer-readable storagemedia, described below, depending on whether, for example, data accessneeds to be bi-directional or uni-directional. For example, processor702 can also directly and very rapidly retrieve and store frequentlyneeded data in a cache memory, not shown.

A removable mass storage device 712 provides additional data storagecapacity for the computer system 700, and is coupled eitherbi-directionally (read/write) or uni-directionally (read only) toprocessor 702. For example, storage 712 can also includecomputer-readable media such as magnetic tape, flash memory, PC-CARDS,portable mass storage devices, holographic storage devices, and otherstorage devices. A fixed mass storage 720 can also, for example, provideadditional data storage capacity. The most common example of massstorage 720 is a hard disk drive. Mass storages 712, 720 generally storeadditional programming instructions, data, and the like that typicallyare not in active use by the processor 702. It will be appreciated thatthe information retained within mass storages 712, 720 can beincorporated, if needed, in standard fashion as part of primary storage710, for example RAM, as virtual memory.

In addition to providing processor 702 access to storage subsystems, bus714 can be used to provide access to other subsystems and devices aswell. As shown, these can include a display monitor 718, a networkinterface 716, a keyboard 704, and a pointing device 706, as well as anauxiliary input/output device interface, a sound card, speakers, andother subsystems as needed. For example, the pointing device 706 can bea mouse, stylus, track ball, trackpad, or tablet, and is useful forinteracting with a graphical user interface.

The network interface 716 allows processor 702 to be coupled to anothercomputer, computer network, or telecommunications network using anetwork connection as shown. For example, through the network interface716, the processor 702 can receive information, for example data objectsor program instructions, from another network, or output information toanother network in the course of performing method/process steps.Information, often represented as a sequence of instructions to beexecuted on a processor, can be received from and outputted to anothernetwork. An interface card or similar device and appropriate softwareimplemented by, for example executed/performed on, processor 702 can beused to connect the computer system 700 to an external network andtransfer data according to standard protocols. For example, variousprocess embodiments disclosed herein can be executed on processor 702,or can be performed across a network such as the Internet, intranetnetworks, or local area networks in conjunction with a remote processorthat shares a portion of the processing. Throughout this specification,“network” refers to any interconnection between computer componentsincluding the Internet, Ethernet, intranet, local-area network (“LAN”),home-area network (“HAN”), serial connection, parallel connection,wide-area network (“WAN”), Fibre Channel, PCI/PCI-X, AGP, VLbus, PCIExpress, Expresscard, Infiniband, ACCESS.bus, Wireless LAN, WiFi,HomePNA, Optical Fibre, G.hn, infrared network, satellite network,microwave network, cellular network, virtual private network (“VPN”),Universal Serial Bus (“USB”), FireWire, Serial ATA, 1-Wire, UNI/O, orany form of connecting homogenous, heterogeneous systems and/or groupsof systems together. Additional mass storage devices, not shown, canalso be connected to processor 702 through network interface 716.

An auxiliary I/O device interface, not shown, can be used in conjunctionwith computer system 700. The auxiliary I/O device interface can includegeneral and customized interfaces that allow the processor 702 to sendand, more typically, receive data from other devices such asmicrophones, touch-sensitive displays, transducer card readers, tapereaders, voice or handwriting recognizers, biometrics readers, cameras,portable mass storage devices, and other computers.

In addition, various embodiments disclosed herein further relate tocomputer storage products with a computer readable medium that includesprogram code for performing various computer-implemented operations. Thecomputer-readable medium is any data storage device that can store datawhich can thereafter be read by a computer system. Examples ofcomputer-readable media include, but are not limited to, all the mediamentioned above: magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as optical disks; and specially configured hardware devices such asapplication-specific integrated circuits (“ASIC”s), programmable logicdevices (“PLD”s), and ROM and RAM devices. Examples of program codeinclude both machine code, as produced, for example, by a compiler, orfiles containing higher level code, for example, a script that can beexecuted using an interpreter.

Computer system 700 may comprise one or more sensors 722. The one ormore sensors 722 may be configured to measure orientation, acceleration,tilt, and/or location (e.g., gyroscope, accelerometer, inclinometer,clinometer, GPS, etc.).

The computer system shown in FIG. 7 is but an example of a computersystem suitable for use with the various embodiments disclosed herein.Other computer systems suitable for such use can include additional orfewer subsystems. In addition, bus 714 is illustrative of anyinterconnection scheme serving to link the subsystems. Other computerarchitectures having different configurations of subsystems can also beutilized.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system, comprising: a communication interfaceconfigured to receive location data associated with an on-demandelectric vehicle and an indication that an on-demand electric vehiclehas fallen, wherein the indication that an on-demand electric vehiclehas fallen includes data associated with one or more sensors of theon-demand electric vehicle; and a processor coupled to the communicationinterface, wherein the processor is configured to: determine that arental associated with the on-demand electric vehicle has ended; andprovide via a user interface information indicating that the on-demandelectric vehicle is in a fallen position.
 2. The system of claim 1,wherein the one or more sensors includes at least one of an accelerationsensor, an orientation sensor, and/or a tilt sensor.
 3. The system ofclaim 1, wherein the communication interface is configured to receive aselection of the on-demand electric vehicle.
 4. The system of claim 3,wherein the processor is configured to update information provided bythe user interface based on the received selection.
 5. The system ofclaim 3, wherein the communication interface is configured to receive anindication that the selected fallen on-demand electric vehicle is in anup-right position.
 6. The system of claim 5, wherein the indication thatthe selected fallen on-demand electric vehicle is in an up-rightposition includes data associated with one or more sensors of theon-demand electric vehicle.
 7. The system of claim 5, wherein theindication that the selected fallen on-demand electric vehicle is in anup-right position includes an image of the fallen on-demand electricvehicle in the up-right position.
 8. The system of claim 5, wherein theprocessor is configured to provide an incentive associated with theselected fallen on-demand electric vehicle.
 9. The system of claim 1,wherein the processor is configured to update a database in response tothe rental associated with the on-demand electric vehicle ending. 10.The system of claim 1, wherein the communication interface is configuredto receive a selection of a plurality of on-demand electric vehicles,wherein the selected plurality of on-demand electric vehicles includesthe fallen on-demand electric vehicle.
 11. The system of claim 10,wherein the processor is configured to determine a route indicating anorder in which the plurality of on-demand electric vehicles are to beserviced based on corresponding locations associated with the pluralityof on-demand electric vehicles.
 12. The system of claim 11, wherein theprocessor is configured provide the determined route via the userinterface.
 13. The system of claim 10, wherein the communicationinterface is configured to receive corresponding indications that theplurality of on-demand electric vehicles are in an up-right position.14. The system of claim 13, wherein the processor is configured toprovide corresponding incentives associated with each of the pluralityof on-demand electric vehicles.
 15. A method, comprising: receivinglocation data associated with an on-demand electric vehicle and anindication that an on-demand electric vehicle has fallen, wherein theindication that an on-demand electric vehicle has fallen includes dataassociated with one or more sensors of the on-demand electric vehicle;determining that a rental associated with the on-demand electric vehiclehas ended; and providing via a user interface information indicatingthat the on-demand electric vehicle is in a fallen position.
 16. Themethod of claim 15, further comprising receiving a selection of theon-demand electric vehicle.
 17. The method of claim 15, furthercomprising receiving an indication that the selected fallen on-demandelectric vehicle is in an up-right position.
 18. A computer programproduct, the computer program product being embodied in a non-transitorycomputer readable storage medium and comprising computer instructionsfor: receiving location data associated with an on-demand electricvehicle and an indication that an on-demand electric vehicle has fallen,wherein the indication that an on-demand electric vehicle has fallenincludes data associated with one or more sensors of the on-demandelectric vehicle; determining that a rental associated with theon-demand electric vehicle has ended; and providing via a user interfaceinformation indicating that the on-demand electric vehicle is in afallen position.